Enclave pool shared key

ABSTRACT

In one example, an enclave pool is formed. The enclave pool may include a plurality of enclaves. Each enclave may have a private enclave key and a public enclave key. A shared enclave pool key may be generated from or otherwise based on the public enclave key of each enclave of the enclave pool. A first enclave may be allocated from the enclave pool to a first cryptlet. A payload of the first enclave is received. The payload of the first enclave may be signed with a first digital signature by the private enclave key of the first enclave. A payload of the second enclave may be received. The payload of the second enclave may be signed with a second digital signature by the private enclave key of the second enclave. The first digital signature and the second signature may be validated via the shared enclave pool key.

BACKGROUND

Blockchain systems have been proposed for a variety of applicationscenarios, including applications in the financial industry, healthcare, IoT, and so forth. For example, the Bitcoin system was developedto allow electronic cash to be transferred directly from one party toanother without going through a financial institution. A bitcoin (e.g.,an electronic coin) is represented by a chain of transactions thattransfers ownership from one party to another party. To transferownership of a bitcoin, a new transaction may be generated and added toa stack of transactions in a block. The new transaction, which includesthe public key of the new owner, may be digitally signed by the ownerwith the owner's private key to transfer ownership to the new owner asrepresented by the new owner public key.

Once the block is full, the block may be “capped” with a block headerthat is a hash digest of all the transaction identifiers within theblock. The block header may be recorded as the first transaction in thenext block in the chain, creating a mathematical hierarchy called a“blockchain.” To verify the current owner, the blockchain oftransactions can be followed to verify each transaction from the firsttransaction to the last transaction. The new owner need only have theprivate key that matches the public key of the transaction thattransferred the bitcoin. The blockchain may create a mathematical proofof ownership in an entity represented by a security identity (e.g., apublic key), which in the case of the bitcoin system ispseudo-anonymous.

SUMMARY OF THE DISCLOSURE

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used to limit the scope of the claimed subject matter.

Briefly stated, the disclosed technology is generally directed to securetransactions. In one example of the technology, an enclave pool isformed. The enclave pool may include a plurality of enclaves that aresecure execution environments. In some examples, each enclave has anenclave key pair including a private enclave key and a public enclavekey. A shared enclave pool key may be generated from or otherwise basedon the public enclave key of each enclave of the enclave pool. A firstenclave may be allocated from the enclave pool to a first cryptlet. Apayload of the first enclave may be received. The payload of the firstenclave may be signed with first digital signature by the privateenclave key of the first enclave. A payload of the second enclave isreceived. The payload of the second enclave may be signed with a seconddigital signature by the private enclave key of the second enclave. Thefirst digital signature and the second signature may be validated viathe shared enclave pool key.

In some examples, a cryptlet is a code component that can execute in asecure environment and be communicated with using secure channels. Oneapplication for cryptlets is smart contracts. In some examples, the codethat represents this smart contract is written as a cryptlet that hasits own key pair, public and private, to identify that specific cryptlet(logic) which is recorded in the Smart Contract on the blockchain. Insome examples, a smart contract is computer code that partially or fullyexecutes and partially or fully enforces an agreement or transaction,such as an exchange of money and/or property, and which may make use ofblockchain technology. Rather than running the logic of a smart contractin the blockchain itself, in some examples, the logic may instead bedone by cryptlets executing off of the blockchain. In some examples, theblockchain may still be involved in some manner, such as in tracking thestate, and receiving the output of the cryptlet.

Some or all of the cryptlet code may be associated with a constraint toexecute in a secure environment. Accordingly, some of the cryptlet codemay be run in an enclave. In some examples, an enclave is an executionenvironment, provided by hardware or software, that is private, tamperresistant, and secure from external interference. In some examples,outputs from the cryptlet code are signed by at least the host enclave'sprivate enclave key of an enclave key pair stored by the host enclave.The outputs can be attested to out of band from the blockchain, e.g.,the public key of the enclave. Enclaves for use by cryptlets may bepooled in some examples. Pooling of enclaves may allow for enclaves tobe provisioned on demand, e.g., at runtime, based on the secure computeneeds of running applications. When enclaves are pooled, a sharedenclave pool key may be generated from or otherwise based on the publickey of each enclave in the enclave pool.

A cryptlet can request an enclave from an associated enclave pool whenneeded. The request may specify a particular size or type of enclave.For example, some types of enclaves are more secure than others, and maybe associated with a greater cost, and so an enclave having a particularlevel of security may be requested according to the requirements of thecryptlet. When the request is made, a suitable enclave can be fetchedfrom the enclave pool and allocated to the cryptlet based on therequirements of the cryptlet.

Cryptlet code that is to be executed in an enclave can then be executedin the allocated enclave. The payload of the host enclave can then bedigitally signed by at least the private enclave key of the hostenclave. In some cases, this same cryptlet code may be run in anotherenclave. Accordingly, another suitable enclave may be fetched from theenclave pool and allocated to the cryptlet. The cryptlet may thencontinue to execute in the other fetched host enclave. The payload ofthe other fetched host enclave can then be digitally signed by at leastthe private enclave key of the other fetched host enclave.

Accordingly, the output of the cryptlet code may contain two or moredigital signatures which each originate from the private key of aseparate enclave from the enclave pool. These digital signatures can allbe validated be comparing them against the shared enclave pool key.

Other aspects of and applications for the disclosed technology will beappreciated upon reading and understanding the attached figures anddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive examples of the present disclosure aredescribed with reference to the following drawings. In the drawings,like reference numerals refer to like parts throughout the variousfigures unless otherwise specified. These drawings are not necessarilydrawn to scale.

For a better understanding of the present disclosure, reference will bemade to the following Detailed Description, which is to be read inassociation with the accompanying drawings, in which:

FIG. 1 is a block diagram illustrating one example of a suitableenvironment in which aspects of the technology may be employed;

FIG. 2 is a block diagram illustrating one example of a suitablecomputing device according to aspects of the disclosed technology;

FIG. 3 is a block diagram illustrating an example of a system;

FIG. 4 is a block diagram illustrating an example of the system of FIG.3; and

FIGS. 5A-5B are an example dataflow for a process, in accordance withaspects of the present disclosure.

DETAILED DESCRIPTION

The following description provides specific details for a thoroughunderstanding of, and enabling description for, various examples of thetechnology. One skilled in the art will understand that the technologymay be practiced without many of these details. In some instances,well-known structures and functions have not been shown or described indetail to avoid unnecessarily obscuring the description of examples ofthe technology. It is intended that the terminology used in thisdisclosure be interpreted in its broadest reasonable manner, even thoughit is being used in conjunction with a detailed description of certainexamples of the technology. Although certain terms may be emphasizedbelow, any terminology intended to be interpreted in any restrictedmanner will be overtly and specifically defined as such in this DetailedDescription section. Throughout the specification and claims, thefollowing terms take at least the meanings explicitly associated herein,unless the context dictates otherwise. The meanings identified below donot necessarily limit the terms, but merely provide illustrativeexamples for the terms. For example, each of the terms “based on” and“based upon” is not exclusive, and is equivalent to the term “based, atleast in part, on”, and includes the option of being based on additionalfactors, some of which may not be described herein. As another example,the term “via” is not exclusive, and is equivalent to the term “via, atleast in part”, and includes the option of being via additional factors,some of which may not be described herein. The meaning of “in” includes“in” and “on.” The phrase “in one embodiment,” or “in one example,” asused herein does not necessarily refer to the same embodiment orexample, although it may. Use of particular textual numeric designatorsdoes not imply the existence of lesser-valued numerical designators. Forexample, reciting “a widget selected from the group consisting of athird foo and a fourth bar” would not itself imply that there are atleast three foo, nor that there are at least four bar, elements.References in the singular are made merely for clarity of reading andinclude plural references unless plural references are specificallyexcluded. The term “or” is an inclusive “or” operator unlessspecifically indicated otherwise. For example, the phrases “A or B”means “A, B, or A and B.” As used herein, the terms “component” and“system” are intended to encompass hardware, software, or variouscombinations of hardware and software. Thus, for example, a system orcomponent may be a process, a process executing on a computing device,the computing device, or a portion thereof.

Briefly stated, the disclosed technology is generally directed to securetransactions. In one example of the technology, an enclave pool isformed. The enclave pool may include a plurality of enclaves that aresecure execution environments. In some examples, each enclave has anenclave key pair including a private enclave key and a public enclavekey. A shared enclave pool key may be generated from or otherwise basedon the public enclave key of each enclave of the enclave pool. A firstenclave may be allocated from the enclave pool to a first cryptlet. Apayload of the first enclave may be received. The payload of the firstenclave may be signed with first digital signature by the privateenclave key of the first enclave. A payload of the second enclave isreceived. The payload of the second enclave may be signed with a seconddigital signature by the private enclave key of the second enclave. Thefirst digital signature and the second signature may be validated viathe shared enclave pool key.

In some examples, a cryptlet is a code component that can execute in asecure environment and be communicated with using secure channels. Oneapplication for cryptlets is smart contracts. In some examples, the codethat represents this smart contract is written as a cryptlet that hasits own key pair, public and private, to identify that specific smartcontract cryptlet. In some examples, a smart contract is computer codethat partially or fully executes and partially or fully enforces anagreement or transaction, such as an exchange of money and/or property,and which may make use of blockchain technology. Rather than running thelogic of a smart contract in the blockchain itself, in some examples,the logic may instead be done by cryptlets executing off of theblockchain. In some examples, the blockchain may still be involved insome manner, such as in tracking the state, and receiving the output ofthe cryptlet.

Some or all of the cryptlet code may be associated with a constraint toexecute in a secure environment. Accordingly, some of the cryptlet codemay be run in an enclave. In some examples, an enclave is an executionenvironment, provided by hardware or software, that is private, tamperresistant, and secure from external interference. In some examples,outputs from the cryptlet code are signed by at least the host enclave'sprivate enclave key of an enclave key pair stored by the host enclave.The outputs can be attested to out of band from the blockchain, e.g.,the public key of the enclave. Enclaves for use by cryptlets may bepooled in some examples. Pooling of enclaves may allow for enclaves tobe provisioned on demand, e.g., at runtime, based on the secure computeneeds of running applications. When enclaves are pooled, a sharedenclave pool key may be generated from or otherwise based on the publickey of each enclave in the enclave pool.

A cryptlet can request an enclave from an associated enclave pool whenneeded. The request may specify a particular size or type of enclave.For example, some types of enclaves are more secure than others, and maybe associated with a greater cost, and so an enclave having a particularlevel of security may be requested according to the requirements of thecryptlet. When the request is made, a suitable enclave can be fetchedfrom the enclave pool and allocated to the cryptlet based on therequirements of the cryptlet.

Cryptlet code that is to be executed in an enclave can then be executedin the allocated enclave. The payload of the host enclave can then bedigitally signed by at least the private enclave key of the hostenclave. In some cases, this same cryptlet code may be run in anotherenclave. Accordingly, another suitable enclave may be fetched from theenclave pool and allocated to the cryptlet. The cryptlet may thencontinue to execute in the other fetched host enclave. The payload ofthe other fetched host enclave can then be digitally signed by at leastthe private enclave key of the other fetched host enclave.

Accordingly, the output of the cryptlet code may contain two or moredigital signatures which each originate from the private key of aseparate enclave from the enclave pool. These digital signatures can allbe validated be comparing them against the shared enclave pool key.

Illustrative Devices/Operating Environments

FIG. 1 is a diagram of environment 100 in which aspects of thetechnology may be practiced. As shown, environment 100 includescomputing devices 110, as well as network nodes 120, connected vianetwork 130. Even though particular components of environment 100 areshown in FIG. 1, in other examples, environment 100 can also includeadditional and/or different components. For example, in certainexamples, the environment 100 can also include network storage devices,maintenance managers, and/or other suitable components (not shown).Computing devices no shown in FIG. 1 may be in various locations,including on premise, in the cloud, or the like. For example, computerdevices no may be on the client side, on the server side, or the like.

As shown in FIG. 1, network 130 can include one or more network nodes120 that interconnect multiple computing devices no, and connectcomputing devices no to external network 140, e.g., the Internet or anintranet. For example, network nodes 120 may include switches, routers,hubs, network controllers, or other network elements. In certainexamples, computing devices no can be organized into racks, actionzones, groups, sets, or other suitable divisions. For example, in theillustrated example, computing devices 110 are grouped into three hostsets identified individually as first, second, and third host sets 112a-112 c. In the illustrated example, each of host sets 112 a-112 c isoperatively coupled to a corresponding network node 120 a-120 c,respectively, which are commonly referred to as “top-of-rack” or “TOR”network nodes. TOR network nodes 120 a-120C can then be operativelycoupled to additional network nodes 120 to form a computer network in ahierarchical, flat, mesh, or other suitable types of topology thatallows communications between computing devices no and external network140. In other examples, multiple host sets 112 a-112C may share a singlenetwork node 120. Computing devices 110 may be virtually any type ofgeneral- or specific-purpose computing device. For example, thesecomputing devices may be user devices such as desktop computers, laptopcomputers, tablet computers, display devices, cameras, printers, orsmartphones. However, in a data center environment, these computingdevices may be server devices such as application server computers,virtual computing host computers, or file server computers. Moreover,computing devices no may be individually configured to providecomputing, storage, and/or other suitable computing services.

In some examples, one or more of the computing devices no is an IoTdevice, a device that comprises part or all of an IoT support service, adevice comprising part or all of an application back-end, or the like,as discussed in greater detail below.

Illustrative Computing Device

FIG. 2 is a diagram illustrating one example of computing device 200 inwhich aspects of the technology may be practiced. Computing device 200may be virtually any type of general- or specific-purpose computingdevice. For example, computing device 200 may be a user device such as adesktop computer, a laptop computer, a tablet computer, a displaydevice, a camera, a printer, or a smartphone. Likewise, computing device200 may also be server device such as an application server computer, avirtual computing host computer, or a file server computer, e.g.,computing device 200 may be an example of computing device 110 ornetwork node 120 of FIG. 1. Computing device 200 may also be an IoTdevice that connects to a network to receive IoT services. Likewise,computer device 200 may be an example any of the devices illustrated inor referred to in FIGS. 3-5, as discussed in greater detail below. Asillustrated in FIG. 2, computing device 200 includes processing circuit210, operating memory 220, memory controller 230, data storage memory250, input interface 260, output interface 270, and network adapter 280.Each of these afore-listed components of computing device 200 includesat least one hardware element.

Computing device 200 includes at least one processing circuit 210configured to execute instructions, such as instructions forimplementing the herein-described workloads, processes, or technology.Processing circuit 210 may include a microprocessor, a microcontroller,a graphics processor, a coprocessor, a field-programmable gate array, aprogrammable logic device, a signal processor, or any other circuitsuitable for processing data. Processing circuit 210 is an example of acore. The aforementioned instructions, along with other data (e.g.,datasets, metadata, operating system instructions, etc.), may be storedin operating memory 220 during run-time of computing device 200.Operating memory 220 may also include any of a variety of data storagedevices/components, such as volatile memories, semi-volatile memories,random access memories, static memories, caches, buffers, or other mediaused to store run-time information. In one example, operating memory 220does not retain information when computing device 200 is powered off.Rather, computing device 200 may be configured to transfer instructionsfrom a non-volatile data storage component (e.g., data storage component250) to operating memory 220 as part of a booting or other loadingprocess.

Operating memory 220 may include 4^(th) generation double data rate(DDR4) memory, 3^(rd) generation double data rate (DDR3) memory, otherdynamic random access memory (DRAM), High Bandwidth Memory (HBM), HybridMemory Cube memory, 3D-stacked memory, static random access memory(SRAM), or other memory, and such memory may comprise one or more memorycircuits integrated onto a DIMM, SIMM, SODIMM, or other packaging. Suchoperating memory modules or devices may be organized according tochannels, ranks, and banks. For example, operating memory devices may becoupled to processing circuit 210 via memory controller 230 in channels.One example of computing device 200 may include one or two DIMMs perchannel, with one or two ranks per channel. Operating memory within arank may operate with a shared clock, and shared address and commandbus. Also, an operating memory device may be organized into severalbanks where a bank can be thought of as an array addressed by row andcolumn. Based on such an organization of operating memory, physicaladdresses within the operating memory may be referred to by a tuple ofchannel, rank, bank, row, and column.

Despite the above-discussion, operating memory 220 specifically does notinclude or encompass communications media, any communications medium, orany signals per se.

Memory controller 230 is configured to interface processing circuit 210to operating memory 220. For example, memory controller 230 may beconfigured to interface commands, addresses, and data between operatingmemory 220 and processing circuit 210. Memory controller 230 may also beconfigured to abstract or otherwise manage certain aspects of memorymanagement from or for processing circuit 210. Although memorycontroller 230 is illustrated as single memory controller separate fromprocessing circuit 210, in other examples, multiple memory controllersmay be employed, memory controller(s) may be integrated with operatingmemory 220, or the like. Further, memory controller(s) may be integratedinto processing circuit 210. These and other variations are possible.

In computing device 200, data storage memory 250, input interface 260,output interface 270, and network adapter 280 are interfaced toprocessing circuit 210 by bus 240. Although, FIG. 2 illustrates bus 240as a single passive bus, other configurations, such as a collection ofbuses, a collection of point to point links, an input/output controller,a bridge, other interface circuitry, or any collection thereof may alsobe suitably employed for interfacing data storage memory 250, inputinterface 260, output interface 270, or network adapter 280 toprocessing circuit 210.

In computing device 200, data storage memory 250 is employed forlong-term non-volatile data storage. Data storage memory 250 may includeany of a variety of non-volatile data storage devices/components, suchas non-volatile memories, disks, disk drives, hard drives, solid-statedrives, or any other media that can be used for the non-volatile storageof information. However, data storage memory 250 specifically does notinclude or encompass communications media, any communications medium, orany signals per se. In contrast to operating memory 220, data storagememory 250 is employed by computing device 200 for non-volatilelong-term data storage, instead of for run-time data storage.

Also, computing device 200 may include or be coupled to any type ofprocessor-readable media such as processor-readable storage media (e.g.,operating memory 220 and data storage memory 250) and communicationmedia (e.g., communication signals and radio waves). While the termprocessor-readable storage media includes operating memory 220 and datastorage memory 250, the term “processor-readable storage media,”throughout the specification and the claims whether used in the singularor the plural, is defined herein so that the term “processor-readablestorage media” specifically excludes and does not encompasscommunications media, any communications medium, or any signals per se.However, the term “processor-readable storage media” does encompassprocessor cache, Random Access Memory (RAM), register memory, and/or thelike.

Computing device 200 also includes input interface 260, which may beconfigured to enable computing device 200 to receive input from users orfrom other devices. In addition, computing device 200 includes outputinterface 270, which may be configured to provide output from computingdevice 200. In one example, output interface 270 includes a framebuffer, graphics processor, graphics processor or accelerator, and isconfigured to render displays for presentation on a separate visualdisplay device (such as a monitor, projector, virtual computing clientcomputer, etc.). In another example, output interface 270 includes avisual display device and is configured to render and present displaysfor viewing. In yet another example, input interface 260 and/or outputinterface 270 may include a universal asynchronous receiver/transmitter(“UART”), a Serial Peripheral Interface (“SPI”), Inter-IntegratedCircuit (“I2C”), a General-purpose input/output (GPIO), and/or the like.Moreover, input interface 260 and/or output interface 270 may include orbe interfaced to any number or type of peripherals.

In the illustrated example, computing device 200 is configured tocommunicate with other computing devices or entities via network adapter280. Network adapter 280 may include a wired network adapter, e.g., anEthernet adapter, a Token Ring adapter, or a Digital Subscriber Line(DSL) adapter. Network adapter 280 may also include a wireless networkadapter, for example, a Wi-Fi adapter, a Bluetooth adapter, a ZigBeeadapter, a Long Term Evolution (LTE) adapter, or a 5G adapter.

Although computing device 200 is illustrated with certain componentsconfigured in a particular arrangement, these components and arrangementare merely one example of a computing device in which the technology maybe employed. In other examples, data storage memory 250, input interface260, output interface 270, or network adapter 280 may be directlycoupled to processing circuit 210, or be coupled to processing circuit210 via an input/output controller, a bridge, or other interfacecircuitry. Other variations of the technology are possible.

Some examples of computing device 200 include at least one memory (e.g.,operating memory 220) adapted to store run-time data and at least oneprocessor (e.g., processing unit 210) that is adapted to executeprocessor-executable code that, in response to execution, enablescomputing device 200 to perform actions.

Illustrative Systems

FIG. 3 is a block diagram illustrating an example of a system (300).System 300 may include network 330, as well as participant devices 311and 312, member devices 341 and 342, validation nodes (VNs) 351 and 352,enclaves 371 and 372, cryptlet fabric devices 361 and 362, and key vault365, which all may connect to network 330.

Each of the participant devices 311 and 312, member devices 341 and 342,VNs 351 and 352, cryptlet fabric devices 361 and 362, and/or key vault365 may include examples of computing device 200 of FIG. 2. FIG. 3 andthe corresponding description of FIG. 3 in the specification illustratesan example system for illustrative purposes that does not limit thescope of the disclosure.

Network 330 may include one or more computer networks, including wiredand/or wireless networks, where each network may be, for example, awireless network, local area network (LAN), a wide-area network (WAN),and/or a global network such as the Internet. On an interconnected setof LANs, including those based on differing architectures and protocols,a router acts as a link between LANs, enabling messages to be sent fromone to another. Also, communication links within LANs typically includetwisted wire pair or coaxial cable, while communication links betweennetworks may utilize analog telephone lines, full or fractionaldedicated digital lines including T1, T2, T3, and T4, IntegratedServices Digital Networks (ISDNs), Digital Subscriber Lines (DSLs),wireless links including satellite links, or other communications linksknown to those skilled in the art. Furthermore, remote computers andother related electronic devices could be remotely connected to eitherLANs or WANs via a modem and temporary telephone link. Network 330 mayinclude various other networks such as one or more networks using localnetwork protocols such as 6LoWPAN, ZigBee, or the like. Some IoT devicesmay be connected to a user device via a different network in network 330than other IoT devices. In essence, network 330 includes anycommunication technology by which information may travel betweenparticipant devices 311 and 312, member devices 341 and 342, VNs 351 and352, cryptlet fabric devices 361 and 362, enclaves 371 and 372, and/orkey vault 365. Although each device or service is shown connected asconnected to network 330, that does not mean that each devicecommunicates with each other device shown. In some examples, somedevices/services shown only communicate with some other devices/servicesshown via one or more intermediary devices. Also, although network 330is illustrated as one network, in some examples, network 330 may insteadinclude multiple networks that may or may not be connected with eachother, with some of the devices shown communicating with each otherthrough one network of the multiple networks and other of the devicesshown communicating with each other with a different network of themultiple networks.

In some examples, VNs 351 and VN 352 are part of a blockchain network.In some examples, VNs 351 and 352 are devices that, during normaloperation, validate and process submitted blockchain transactions, andexecute chaincode. In some examples, member devices 341 and 342 aredevices used by members to communicate over network 330, such as forcommunication between a member and its corresponding VN, for example toendorse a VN. In some examples, participant devices 311 and 312 aredevices used by participants to communicate over network 330, such as torequest a transaction.

An example arrangement of system 300 may be described as follows. Insome examples, enclaves 371 and 372 are execution environments, providedby hardware or software, that are private, tamper resistant, and securefrom external interference. Outputs from an enclave are digitally signedby the enclave. Cryptlet fabric devices 361 and 362 are part of acryptlet fabric that provides runtime and other functionality forcryptlets, as discussed in greater detail below. Key vault 365 may beused to provide secure persistent storage for keys used by cryptlets foridentity, digital signature, and encryption services.

System 300 may include more or less devices than illustrated in FIG. 3,which is shown by way of example only.

Illustrative Device

FIG. 4 is a block diagram illustrating an example of system 400, whichmay be employed as an example of system 300 of FIG. 3. System 400 mayinclude participant devices 411 and 412, member devices 441 and 442,blockchain network 450, cryptlet fabric 460, enclaves 470, and key vault465.

In some examples, during normal operation, blockchain network 450 mayvalidate and process submitted blockchain transactions. In someexamples, member devices 441 and 442 are devices used by members tocommunicate with blockchain network 450. In some examples, participantdevices 411 and 412 are devices used by participants to communicate withblockchain network 450, such as to request a transaction. In someexamples, enclaves 470 are execution environments, provided by hardwareor software, that are private, tamper resistant, and secure fromexternal interference. In some examples, outputs from an enclave aredigitally signed by the enclave. Key vault 465 may be used to providesecure persistent storage for keys used by cryptlets for identity,digital signature, and encryption services.

Blockchain network 450 may include a number of VNs. In some examples,each member of blockchain network 450 may, via a member device (e.g.,441 or 442), maintain one or more VNs in blockchain network 450.Participants may request, via participant devices (e.g., 411 or 412) fortransactions to be performed by blockchain network 450. During normaloperation, VNs in blockchain network 450 validate and process submittedtransactions, and execute logic code.

Transactions performed by the blockchain network 450 may be stored inblockchains. In some examples, blockchains are decentralized ledgersthat record transactions performed by the blockchain in a verifiablemanner. Multiple transactions may be stored in a block. Once a block isfull, the block may be capped with a block header that is a hash digestof all of the transaction identifiers within a block. The block headermay be recorded as the first transaction in the next block in the chain,thus creating a blockchain.

A blockchain network may also be used for the processing of smartcontracts. In some examples, a smart contract is computer code thatpartially or fully executes and partially or fully enforces an agreementor transaction, such as an exchange of money and/or property, and whichmay make use of blockchain technology. Rather than running the logic ofa smart contract in the blockchain itself, the logic may instead, withassistance from cryptlet fabric 460, be done by cryptlets executing offof the blockchain network 450. In some examples, a cryptlet is a codecomponent that can execute in a secure environment and be communicatedwith using secure channels. In some examples, cryptlet fabric 460 isconfigured to provide runtime and other functionality for cryptlets.

In some examples, Cryptlet Fabric 460 a server-less cloud platform thatprovides core infrastructure for middleware that enablesblockchain-based applications with increased functionality. In someexamples, Cryptlet Fabric 460 is comprised of several componentsproviding the functionality for an enhanced security envelop ofblockchain application into the cloud as well as a common applicationprogram interface (API) that abstracts the underlying blockchain and itsnuance from developers.

In some examples, Cryptlet Fabric 460 manages scale, failover, caching,monitoring, and/or management of cryptlets, as well as a run time securekey platform for cryptlets that allows for the creation, persistence,and hydration of private keys at scale. (“Hydration” refers to theactivation and orchestration in memory from persistent storage.) Thisallows cryptlets to create, store and use key pairs in a secureexecution environment to perform a variety of functions including, forexample, digital signatures, ring signatures, zero knowledge proofs,threshold, and homomorphic encryption.

In some examples, a cryptlet may be a software component that inheritsfrom base classes and implements interfaces that provide cryptographicprimitives and integrations for distributed trust applications. In someexamples, it is sufficient for developers to know the base classes andhow to implement required and optional interfaces for cryptlets todevelop on the platform. Established software development frameworks,patterns, and designs can be used for user interfaces and integrationinto existing systems.

Types of cryptlets may include utility cryptlets and contract cryptlets.Utility cryptlets usually perform external data integration via eventsinternal or external, provide data access or reusable logic toblockchain smart contracts, but can also provide service level APIs forother systems to work with blockchains. Utility cryptlets whose primarypurpose is to inject attested data into blockchains may be called“oracle” cryptlets. In some examples, contract cryptlets contain smartcontract specific logic that counter-parties signing the contract agreeto. Both types of cryptlets may provide a blockchain facing API and aSurface level API.

Regardless of how a smart contract is implemented, utility cryptlets maybe used to provide information and additional computation for smartcontracts in reusable libraries. These libraries may be used to create aframework for building distributed applications and exposed in a commonway via the Cryptlet Fabric 460 in both public and private cloud, and inblockchain environments.

Contract cryptlets may redefine the implementation of the logic that asmart contract executes. In some examples, these cryptlets prescribethat any logic be run off-chain, using the underlying blockchain as adatabase.

Utility cryptlets may provide discrete functionality like providingexternal information, e.g., market prices, external data from othersystems, or proprietary formulas. These may be called “blockchainoracles” in that they can watch and inject “real world” events and datainto blockchain systems. Smart contracts may interact with these using aPublish/Subscribe pattern where the utility cryptlet publishes an eventfor subscribing smart contracts. The event triggers may be external tothe blockchain (e.g., a price change) or internal to the blockchain(e.g., a data signal) within a smart contract or operation code.

In some examples, these cryptlets can also be called directly by othercryptlets within the fabric and expose an external or surface level APIthat other systems can call. For example, an enterprise Customerrelationship management (CRM) system may publish an event to asubscribing cryptlet that in turn publishes information to a blockchainin blockchain network 450 based on that information. Bi-directionalintegration may be provided to smart contracts and blockchains throughCryptlet Fabric 460 in this way.

Contract or control cryptlets may represent the entire logic or state ina contractual agreement between counter parties. In some examples,contract cryptlets used in smart contract-based systems can use theblockchain ledger to authentically store a contract's data using smartcontract logic for data validity, but surrogate logic to a contractcryptlet providing “separation of concerns” within an application'sdesign. The relationship between an on-chain smart contract and acontract cryptlet may be called a trust relationship.

For non-smart contract based systems, in some examples, contractcryptlets perform logic and write their data to the blockchain withoutthe smart contract or well-defined schema on the blockchain.

In essence, in some examples, contract cryptlets can run the logic of acontractual agreement between counterparties at scale, in a privatesecure environment, yet store its data in the underlying blockchainregardless of type.

In some examples, a cryptlet has common properties regardless of type:

Identity—For example, a key pair. The identity can be created by thecryptlet itself or assigned. The public key is also known as thecryptlet address in some examples. The private key may be used to signall transactions from the cryptlet. Private keys may be stored in theKeyVault 465 or otherwise fetched via secure channel when rehydrating orassigning identity to a cryptlet.

Name—A common name that is mapped to the address for a more readableidentity in some examples.

Code—code written in a language that's its Parent Container supports insome examples.

CryptletBindings—a small list of bindings that represent the client(e.g., blockchain contracts or accounts) addresses and parameters forthe binding in some examples.

Events—List of events published or watched by the cryptlet in someexamples. These event triggers can be watched blockchain data or eventsor external in some examples.

API—A set of surface level APIs that non-blockchain systems or othercryptlets can use as well as subscriber call back methods in someexamples.

Parent Container—A cryptlet container that the cryptlet runs in, in someexamples.

Manifest—simple JavaScript Object Notation (JSON) configuration settingsfor a cryptlet that is used for deployment into the fabric, in someexamples.

A cryptlet container may provide a runtime for Cryptlets to execute in.Cryptlet containers may provide abstractions for Cryptlets like I/O,security, key management, and runtime optimization.

Cryptlet containers may provide secure key storage and retrieval forcryptlets to use for identity, digital signatures and encryption.Cryptlets may automatically store and fetch keys via the cryptletcontainer which integrates with the key vault 465 via a secure channelor CryptletTunnel.

A cryptlet may declare in the manifest its configuration, enclaving,type, etc. In some examples, the cryptlet container ensures that thedependencies the cryptlet needs are in place for it to run.

Enclave requirements for a cryptlet may be set in the cryptlet manifestor in policy. Enclave options and configuration are set in the cryptletcontainer service, which is part of Cryptlet Fabric 460 in someexamples.

In some examples, the cryptlet container service is the hub of theCryptlet Fabric 460. In some examples, the primary duties and componentsof the cryptlet container service are:

-   -   Cryptlet Fabric Registry, which is the Registry and Database for        configuration.        -   Cryptlets: Name and ID, Surface Level API, and Events they            expose to blockchain networks.        -   Blockchains or other distributed ledgers: Network Name,            Type, Node List, metadata.        -   Smart contracts: on-chain smart contract addresses and            application binary interfaces (Allis) or other interface            definition that subscribe to or have trust relationships            with Cryptlets as well as the host blockchain network.    -   CryptletBindings, which is a collection of all bindings the        fabric serves. A CryptletBinding may map smart contracts to        cryptlets or cryptlets to cryptlets for validation and message        routing. A CryptletBinding may represent a single binding        between a smart contract and a cryptlet (or pair/ring). Details        about the binding like subscription parameter(s), interface        parameter(s), and/or smart contract address are used to route        messages between cryptlets, their clients, smart contracts, or        other cryptlets.    -   Secure Compute Registry: is a registry of enclaves and their        attributes like capabilities, version, costs, and configuration.        Enclave pool definitions of clusters and additional        cryptographic services provided by Enclave Pools like key        derivation, ring signatures, and threshold encryption.    -   Cryptlet Catalog, which may be a REpresentational State Transfer        (REST) API and/or Web Site for developers to discover and enlist        cryptlets into their applications either for a smart contract        binding or for use in building a user interface or integration.    -   API for abstracting blockchain transaction formatting and        Atomicity, Consistency, Isolation, Durability (ACID) delivery        append transactions and read queries from cryptlets and any        other system wanting “direct” access to the underlying        blockchain. This API can be exposed in various ways, e.g.,        messaging via service bus, Remote Procedure Calls (RPCs), and/or        REST.

Cryptlets, blockchains and smart contracts may get registered with thecryptlet fabric registry service. The cryptlet container service maypublish the Cryptlet Catalog for on-chain smart contract, front end userinterface (UI) and systems integration developers discover and usecryptlets. Developers using the service level APIs may interact with theblockchain via cryptlets and not be concerned or even necessarily knowthey are working with blockchain data. User Interfaces and Integrationsto other systems may interact with cryptlet surface level APIs torapidly integrate and build applications.

Enclaves may be hardware or software. For example, a software enclavecan be formed by running a hypervisor or Virtual Secure Machine (VSM).An example of a hardware enclave is a secure hardware enclave such asSGX from Intel. A hardware enclave may have a set of keys that areburned/etched onto the silicon than can be used to sign output from theenclave to serve as an attestation to its secure execution. Usually,there is a 1-1 ratio of code and the enclave it runs in. However, in thecloud, cryptlets may be instantiated dynamically and may or may not getthe same hardware enclave.

In some examples, enclave resources are pooled together and categorizedbased on their capabilities. For example, there may be VSM enclaves andhardware enclaves which may have different performance or memoryenhancements over time. Cryptlets may be configured to request anyenclave or a specific type of enclave and potentially a higherperformance hardware enclave at runtime.

In some examples, enclaves are secure execution environments where codecan be run in an isolated, private environment and the results of thesecure execution can be attested to have been run unaltered and inprivate. This means that secrets like private keys can be created andused within an enclave to sign transactions and be proved to thirdparties to have run within an enclave.

In some examples, to deliver cryptlets at scale, enclaves are pooled bythe Cryptlet Fabric 460 upon receiving an enclave pool request. In someexamples, an enclave pool acts as a resource where, upon receiving anenclave request for a cryptlet, an enclave can be fetched from theenclave pool by Cryptlet Fabric 460 and allocated to a cryptlet atruntime based on the requirements of that cryptlet.

For example, a policy can be set that all cryptlets running a smartcontract between counterparty A and B always requires an SGX V2 Enclavefrom Intel. Alternatively, the enclave requirement may be leftunspecified, so that the least cost (e.g., in terms of money, time,already active, etc.) enclave is provided.

Enclaves 470 are registered within the enclave pool. In some examples,an enclave pool shared signature is generated for the enclave pool,where the enclave pool shared signature is derived from the private keyof each enclave in the enclave pool. In some examples, pool managementuses just-in-time (JIT) instantiation of enclaves to use them whenactive, but return them to the pool as soon as the work is done. In someexamples, a cryptlet that has an asynchronous lifespan and that will notcomplete its work can release its enclave at a checkpoint and bere-instantiated in a different enclave. In some examples, switchingenclaves produces different attestations that can be validated by theenclave pool shared signature.

In some examples, when a set of enclaves is registered with the CryptletFabric 460, each enclave public key is recorded in the enclave poolregistry. In some examples, the characteristics are recorded uponregistration and can be modified for pool categories that are notinferred from the hardware. In some examples, once all the enclaves areregistered, the keys for all enclaves are used to generate a key pairfor the pool which is stored in the Key Vault 465.

At runtime, the CryptletContainerService may determine cryptlets runtimeenvironment dependencies based on its registration or policy and requestan enclave out of the enclave pool. The enclave pool may activate anenclave and return its address to the CryptletContainerService, whichmay then inject the appropriate CryptletContainer. In some examples, theCryptletContainer is provided the cryptlet ID and an active binding,which CryptletContainer uses to fetch the cryptlet binary from securestorage, and run a hash code signature check on the cryptlet, which maybe a part of the cryptlet's composite identifier. In some examples, theCryptletContainer then fetches any keys required by the cryptlet fromthe KeyVault 465 and passes them along with the active cryptlet bindinginto the constructor of the cryptlet to instantiate it within theenclave. In some examples, cryptlet code executes in the enclave, andthe payload is digitally signed by the private key of the enclave.

Once a cryptlet is done with its synchronous work, it may call itscheckpoint method which may pass any new keys generated during itssession for the CryptletContainer to persist in the Key Vault 465 aswell as release the cryptlet's enclave back to the pool. By returningthe enclave, the enclave then becomes available again to be used byanother cryptlet.

In some examples, if a Cryptlet requires an enclave that is notavailable and will not be available within a defined call window, anerror is logged, and an exception is thrown.

New enclaves may be added to the enclave pool, which will generate a newshared signature for the pool. In some examples, a shared signature isused when a cryptlet's lifetime spans multiple enclaves and continuityof attestation needs to be established. In some examples, the sharedsignature is historical, so if a cryptlet is attested across multipleenclaves, the shared signature is checked, and if the current signaturedoes not match, the previous version of the signature is checked until amatch is found. In these examples, if no match is found, the attestationchain is not valid.

In this way, in these examples, a rogue enclave cannot contribute to avalidated transaction. In these examples, if a rogue enclave contributesto a transaction, the shared enclave signature would not be made, andthe attestation chain would not be valid.

In some examples, the cryptlet container service has a Blockchain Routerthat provides the abstraction API for data operations againstblockchains. Each different type of blockchain may have a BlockchainMessage Provider or Connector that is plugged into the blockchain routerfor proper message formatting for each blockchain.

In some examples, blockchain connectors have a valid address on each ofthe blockchains the blockchain connector serves and signs transactionswith the key for this address. In some examples, blockchain connectorsrun within an enclave for transaction-signing purposes.

The Blockchain router depends on CryptletBindings for routing messagesto the appropriate blockchain connector. The blockchain connector usesthe CryptletBinding information to format the messages correctly and toensure delivery to the targeted recipient.

In some examples, the cryptlet binding is a data structure that providesthe abstraction between the cryptlet and underlying blockchain, smartcontracts, and accounts. The cryptlet binding may or may not be secureditself, as it may only contain identifier(s) of bound components (e.g.,unique identifier(s)) that authorized parties use to look up detailsfrom other services. In some examples, used in routing messages, thebinding provides the cryptlet ID and the Smart Contract ID itself. Insome examples, the smart contract address is looked up and is bound to aspecific Blockchain ID that maps to a node address.

Data may be enveloped in multiple layers of digital attestations (e.g.,signatures) signed by the data producer or “on-behalf of” a user or IOTdevice, cryptlet, its host enclave and, then the blockchain connector.This layering may be referred to as a signature onion.

The CryptoDelegate, which is a portion of cryptlet fabric 460 in someexamples, may provide an optimization point for verifying these layeredsignatures before passing on to be validated by all of the nodes,accordingly reducing redundant signature checks, rejecting invalidattestation chains, and/or freeing compute resources.

Key Vault 465 may provide secure persistent storage of keys used bycryptlets for identity, digital signatures and encryption services.Cryptlet containers may provide abstractions to cryptlets for storingand fetching keys at runtime. In some examples, a secure communicationchannel, called a CryptletTunnel, is established between the KeyVault465 and the enclave that is hosting the CryptletContainer. In someexamples, storage and retrieval of private keys and secrets used byhosted cryptlets are provided automatically and on demand by theCryptletContainer.

For instance, in some examples, when a cryptlet is instantiated withinits CryptletContainer host, if its identity is established by a key pairin the key vault, the CryptletContainer will securely fetch and providethe key pair to the cryptlet upon instantiation. Or, if the cryptletcreates its own or a new key pair, these new keys may be automaticallystored by the CryptletContainer when the Cryptlet deactivates. In someexamples, the cryptlet can then use the private key to sign transactionsand messages for delivery. One example of an assigned key is a cryptletthat signs transactions as a specific counter party, corporation, user,or device, to a Smart Contract with the counter party's private key.

In some examples, cryptlets can request keys or secrets from theircontainer for other cryptographic services like encryption, decryption,and signing of messages. In some examples, keys used by cryptlets,either for identity or other cryptographic purposes, are looked up andlocated by the CryptletContainer using the CryptletBinding that resolvesto either a Cryptlet Instance ID or a CounterpartyId and requesting orstoring via the CryptletTunnel to KeyVault 465. In some examples, aCryptletBinding Key Graph is used to record key locations for resolvingand locating keys for a different counterparty in a separate Key Vault465 instance that may be controlled by that counterparty. Key derivationfor multiple Cryptlet Identities from a single counterparty may providemultiple concurrence instances to be distinguished. Also, in examplescenarios for one-time use key derivation scenarios where Key Vault 465issues or a cryptlet creates a derived key for cryptlet signing, whenthe signing is done, the derived key is destroyed as it was only inenclave memory. Key life cycle services such as key expiration and resetmay be provided as utilities.

In some examples, developers can construct their smart contracts usingobjects against their logic and simply persist their object state intothe blockchain ledger without having to write a smart contract schema.In some examples, the reverse is also true, and an object model can bebuilt and mapped from an existing smart contract schema. Thisenvironment may provide blockchain portability and ease of developmentfor blockchain solutions.

In some examples, the CryptoDelegate is a set of capabilities that aredelivered differently based on the underlying blockchain or ledger. Insome examples, the CryptoDelegate is part of Cryptlet Fabric 460. Insome examples, the CryptoDelegate functions, in essence, as aclient-side or node-side integration for the Cryptlet Fabric 460. Amongother things, the CryptoDelegate may perform attestation checks onmessages before delivery to the underlying node platform, e.g., blockinginvalid transactions before they get propagated around blockchainnetwork 450.

As discussed above, when an enclave pool is formed, the enclaves in thepool may be registered with the enclave pool. In some examples, when theenclaves are so registered with Cryptlet Fabric 460, each enclave publickey may be received by Cryptlet Fabric 460 and each enclave public keymay be recorded in the enclave pool registry. Additionally, as part ofthe process that occurs when an enclave pool is formed, an enclave poolshared key may be derived from the public key of each enclave in theenclave pool by Cryptlet Fabric 460. A new enclave pool shared key maybe generated by Cryptlet Fabric 460 if the membership of the enclavepool changes.

A cryptlet can request an enclave from an associated enclave pool inresponse to a need. The request may specify a particular size or type ofenclave. For example, some types of enclaves are more secure thanothers, and may be associated with a greater cost, and so an enclavehaving a particular level of security may be requested according to theparticular request. When the request is made, a suitable enclave can befetched by Cryptlet Fabric 460 from the enclave pool and allocated tothe cryptlet based on the particular request.

Cryptlet code that is be executed in an enclave can then be executed inthe allocated enclave. As part of the execution of the cryptlet code,the cryptlet code may generate a payload in the host enclave. Thepayload of the host enclave can then be signed and/or encrypted by thecryptlet private key as well as digitally signed by the private enclavekey of the host enclave. The host enclave can then be deallocated fromthe first cryptlet, so that the cryptlet is no longer running in theenclave, and the enclave is available for other cryptlets. The payloadcan be attested to out-of-band from the blockchain, e.g., with thepublic key of the cryptlet and the public key of the enclave.

In some cases, the cryptlet code may also be run in another enclave. Forinstance, in some examples, as discussed above, pool management may use“just-in-time” (JIT) instantiation of enclaves, but return them to thepool after the work is done. In some examples, a cryptlet that has anasynchronous lifespan and that will not complete its work can deallocateits enclave at a checkpoint.

Accordingly, a different suitable enclave may be fetched from theenclave pool by Cryptlet Fabric 460 and the cryptlet may bere-instantiated in the new enclave. The cryptlet may then continue toexecute in the other host enclave (e.g., the new enclave). The payloadof the other host enclave can then be digitally signed by the privateenclave key of the other host enclave. The other host enclave can thenbe deallocated so that the cryptlet is no longer running in the enclave,and the other host enclave made available for other cryptlets.

In some examples, the cryptlet may be executed by still more enclaves,such as by at least a third enclave in a similar manner as describedabove for the second enclave.

Because the cryptlet in this example is executed in more than oneenclave, the output of the cryptlet code may contain two or more digitalsignatures which each originate from the private key of differentenclaves from the enclave pool, in addition to a digital signatureoriginating from the private cryptlet key, as well as possibly otherdigital signatures as part of the signature onion. In some examples, thedigital signatures that originate from an enclave key from an enclavethat belongs to the enclave pool can all be validated by comparing themagainst the shared enclave pool key. In some examples, the verificationof digital signatures may be performed by the cryptlet fabric.

In some examples, cryptlet code is packaged as a cryptlet that has itsown identity that is a composite of multiple components. In someexamples, the cryptlet identity is the combination of the binary hash ofthe compiled cryptlet, the key pair assigned to that hash, and thebinding identifier.

In some examples, the cryptlet identity composed of these threecomponents allows for a single binary to be compiled and reused acrossmany instances of that contract type.

For an example, for a cryptlet binary financial contract that is anInterest Rate Swap, in one example, the Swap cryptlet would have ahash+keypair that uniquely represents that cryptlet binary in thefabric. In this example, when a new Interest Rate Swap is created, aninstance of that contract is created represented by a binding Id. Thebinding represents the properties/rules of the Swap instance, such asthe identities of the counter parties, where the cryptlet get interestrate pricing from and how often, and/or the like.

In this way, there may be numerous instances of an Interest Rate swapwith a single binary cryptlet executing each of these contracts. Theunique instance is the composite cryptlet identity that represents thecontract in this example.

Accordingly, in some examples, the combination of three components, (1)Binary Hash, (2) Key Pair, and (3) Binding Id, is the instanceidentifier which is then represented as a hash digest for contract thatis recorded on the blockchain ledger representing the version of logiccontrolling the smart contract.

Examples herein have been given of enclave pooling for cryptlets used inconjunction with a blockchain network. However, enclave pooling and theenclave pool shared key may also be used for cryptlets in othercontexts, some of which involve a blockchain network and some of whichdo not involve a blockchain network. That is, enclave pooling and theenclave pool shared key may be used in applications that do not involveblockchain networks or cryptlets.

Illustrative Processes

For clarity, the processes described herein are described in terms ofoperations performed in particular sequences by particular devices orcomponents of a system. However, it is noted that other processes arenot limited to the stated sequences, devices, or components. Forexample, certain acts may be performed in different sequences, inparallel, omitted, or may be supplemented by additional acts orfeatures, whether or not such sequences, parallelisms, acts, or featuresare described herein. Likewise, any of the technology described in thisdisclosure may be incorporated into the described processes or otherprocesses, whether or not that technology is specifically described inconjunction with a process. The disclosed processes may also beperformed on or by other devices, components, or systems, whether or notsuch devices, components, or systems are described herein. Theseprocesses may also be embodied in a variety of ways. For example, theymay be embodied on an article of manufacture, e.g., asprocessor-readable instructions stored in a processor-readable storagemedium or be performed as a computer-implemented process. As analternate example, these processes may be encoded asprocessor-executable instructions and transmitted via a communicationsmedium.

FIGS. 5A-5B are an example dataflow for a process (580). In someexamples, process 580 is performed by a cryptlet fabric, e.g., cryptletfabric 460 of FIG. 4.

In the illustrated example, step 581 occurs first. At step 581, in someexamples, an enclave pool of a plurality of enclaves isformed/generated/created, e.g., to be able to respond to enclaverequests. Also, in some examples, each enclave of the enclave pool hasan enclave key pair including a private enclave key and a public enclavekey.

As shown, step 582 occurs next in some examples. At step 582, in someexamples, a shared enclave pool key is generated from or otherwise basedon the public enclave key of each enclave of the enclave pool. As shown,step 583 occurs next in some examples. At step 583, in some examples, afirst enclave is allocated/assigned from the enclave pool to a firstcryptlet. As shown, step 584 occurs next in some examples. At step 584,in some examples, a payload/output of the first enclave is received. Insome examples, the payload of the first enclave has a first digitalsignature/certificate by the private enclave key of the first enclave.

As shown, step 585 occurs next in some examples. At step 585, in someexamples, a second enclave is allocated from the enclave pool to a firstcryptlet. As shown, step 586 occurs next in some examples. At step 586,in some examples, a payload of the second enclave is received from thesecond enclave. In some examples, the payload of the second enclave hasa second digital signature by the private enclave key of the secondenclave. As shown, step 587 occurs next in some examples. At step 587,in some examples, the first digital signature and the second signatureare validated via the enclave pool shared key.

The process may then proceed to the return block, where other processingis resumed.

CONCLUSION

While the above Detailed Description describes certain examples of thetechnology, and describes the best mode contemplated, no matter howdetailed the above appears in text, the technology can be practiced inmany ways. Details may vary in implementation, while still beingencompassed by the technology described herein. As noted above,particular terminology used when describing certain features or aspectsof the technology should not be taken to imply that the terminology isbeing redefined herein to be restricted to any specific characteristics,features, or aspects with which that terminology is associated. Ingeneral, the terms used in the following claims should not be construedto limit the technology to the specific examples disclosed herein,unless the Detailed Description explicitly defines such terms.Accordingly, the actual scope of the technology encompasses not only thedisclosed examples, but also all equivalent ways of practicing orimplementing the technology.

I claim:
 1. An apparatus, comprising: a device including at least onememory adapted to store run-time data for the device, and at least oneprocessor that is adapted to execute processor-executable code that, inresponse to execution, enables the device to perform actions, including:forming an enclave pool, wherein the enclave pool includes a pluralityof enclaves, wherein the enclaves are secure execution environments, andwherein each enclave of the enclave pool has an enclave key pairincluding a private enclave key and a public enclave key; generating ashared enclave pool key that is derived from the public enclave key ofeach enclave of the enclave pool; allocating a first enclave of theenclave pool to a first cryptlet; receiving a payload of the firstenclave such that the payload of the first enclave has a first digitalsignature by the private enclave key of the first enclave; allocating asecond enclave of the enclave pool to the first cryptlet; receiving apayload of the second enclave such that the payload of the secondenclave has a second digital signature by the private enclave key of thesecond enclave; and validating, via the shared enclave pool key, thefirst digital signature and the second signature.
 2. The apparatus ofclaim 1, the actions further comprising: allocating a third enclave ofthe enclave pool to the first cryptlet; receiving a payload of the thirdenclave such that the payload of the third enclave has a third digitalsignature by the private enclave key of the third enclave; and furthervalidating, via the shared enclave pool key, the third digitalsignature.
 3. The apparatus of claim 1, the actions further comprising:adding a new enclave to the enclave pool to form an updated enclavepool; and generating a new shared enclave pool key from the publicenclave key of each enclave of the updated enclave pool, whereinvalidating the first digital signature and the second digital signatureinclude validating the first digital signature and the second digitalagainst the shared enclave key, and if no match is found, validating thefirst digital signature and the second digital against the new sharedenclave key.
 4. The apparatus of claim 1, the actions furthercomprising: removing an enclave from the enclave pool to form an updatedenclave pool; and generating a new shared enclave pool key from thepublic enclave key of each enclave of the updated enclave pool, whereinvalidating the first digital signature and the second digital signatureinclude validating the first digital signature and the second digitalagainst the shared enclave key, and if no match is found, validating thefirst digital signature and the second digital against the new sharedenclave key.
 5. The apparatus of claim 1, wherein the enclaves of theplurality of enclaves are private, tamper-resistant executionenvironments that are secure from external interference.
 6. Theapparatus of claim 1, wherein each enclave of the plurality of enclavesis at least one of a Virtual Secure Machine or a secure hardwareenclave.
 7. The apparatus of claim 1, wherein the enclaves of theplurality of enclaves are secure execution environments in which codecan be run in an isolated, private environment and for which results ofthe secure execution are capable of being attested to have run unalteredand in private.
 8. The apparatus of claim 1, wherein the first enclaveis a hardware enclave, and wherein the private key of the first enclaveis etched in silicon.
 9. A processor-readable storage medium, havingstored thereon process-executable code that, upon execution by at leastone processor, enables actions, comprising: creating an enclave pool,wherein the enclave pool includes a plurality of enclaves, the enclavesare secure execution environments, and wherein each enclave of theenclave pool stores an enclave key pair including a private enclave keyand a public enclave key; receiving the public enclave key of eachenclave of the enclave pool; generating a shared enclave pool key thatis based upon the public enclave key of each enclave of the enclavepool; assigning a first enclave of the enclave pool to a first cryptlet;receiving a payload of the first enclave such that the payload of thefirst enclave has a first signature by the private enclave key of thefirst enclave; assigning a second enclave of the enclave pool to thefirst cryptlet; receiving a payload of the second enclave such that thepayload of the second enclave has a second signature by the privateenclave key of the second enclave; and using the shared enclave pool keyto validate the first signature and the second signature.
 10. Theprocessor-readable storage medium of claim 9, the actions furthercomprising: allocating a third enclave of the enclave pool to the firstcryptlet; receiving a payload of the third enclave such that the payloadof the third enclave has a third digital signature by the privateenclave key of the third enclave; and further validating, via the sharedenclave pool key, the third digital signature.
 11. Theprocessor-readable storage medium of claim 9, the actions furthercomprising: adding a new enclave to the enclave pool to form an updatedenclave pool; and generating a new shared enclave pool key from thepublic enclave key of each enclave of the updated enclave pool, whereinvalidating the first digital signature and the second digital signatureinclude validating the first digital signature and the second digitalagainst the shared enclave key, and if no match is found, validating thefirst digital signature and the second digital against the new sharedenclave key.
 12. The processor-readable storage medium of claim 9, theactions further comprising: removing an enclave from the enclave pool toform an updated enclave pool; and generating a new shared enclave poolkey from the public enclave key of each enclave of the updated enclavepool, wherein validating the first digital signature and the seconddigital signature include validating the first digital signature and thesecond digital against the shared enclave key, and if no match is found,validating the first digital signature and the second digital againstthe new shared enclave key.
 13. The processor-readable storage medium ofclaim 9, wherein each enclave of the plurality of enclaves is at leastone of a Virtual Secure Machine or a secure hardware enclave.
 14. Theprocessor-readable storage medium of claim 9, wherein the first enclaveis a hardware enclave, and wherein the private key of the first enclaveis etched in silicon.
 15. A method, comprising: forming an enclave pool,wherein the enclave pool includes a plurality of enclaves, wherein theenclaves are secure execution environments, and wherein each enclave ofthe enclave pool has an enclave key pair including a private enclave keyand a public enclave key; generating a shared enclave pool key that isderived from the public enclave key of each enclave of the enclave pool;allocating a first enclave of the enclave pool to a first cryptlet;receiving a payload of the first enclave such that the payload of thefirst enclave has a first digital signature by the private enclave keyof the first enclave; allocating a second enclave of the enclave pool tothe first cryptlet; receiving a payload of the second enclave such thatthe payload of the second enclave has a second digital signature by theprivate enclave key of the second enclave; and validating, via theshared enclave pool key, the first digital signature and the secondsignature.
 16. The method of claim 15, further comprising: allocating athird enclave of the enclave pool to the first cryptlet; receiving apayload of the third enclave such that the payload of the third enclavehas a third digital signature by the private enclave key of the thirdenclave; and further validating, via the shared enclave pool key, thethird digital signature.
 17. The method of claim 15, further comprising:adding a new enclave to the enclave pool to form an updated enclavepool; and generating a new shared enclave pool key from the publicenclave key of each enclave of the updated enclave pool, whereinvalidating the first digital signature and the second digital signatureinclude validating the first digital signature and the second digitalagainst the shared enclave key, and if no match is found, validating thefirst digital signature and the second digital against the new sharedenclave key.
 18. The method of claim 15, further comprising: removing anenclave from the enclave pool to form an updated enclave pool; andgenerating a new shared enclave pool key from the public enclave key ofeach enclave of the updated enclave pool, wherein validating the firstdigital signature and the second digital signature include validatingthe first digital signature and the second digital against the sharedenclave key, and if no match is found, validating the first digitalsignature and the second digital against the new shared enclave key. 19.The method of claim 15, wherein each enclave of the plurality ofenclaves is at least one of a Virtual Secure Machine or a securehardware enclave.
 20. The method of claim 15, wherein the enclaves ofthe plurality of enclaves are secure execution environments in whichcode can be run in an isolated, private environment and for whichresults of the secure execution are capable of being attested to haverun unaltered and in private.